Gate Result: ⚠️ INCONCLUSIVE

Platform: IOS · Base: net11.0 · Merge base: ec79089f

🩺 Could not verify — environment/infrastructure error. The gate ran the tests but hit an environment error (an emulator/simulator/Appium/XHarness flake, a device that would not boot, or an empty/invalid result file), so it could not record a real pass/fail. The ⚠️ ENV ERROR marks below are infrastructure, not test failures — this is not a problem with your PR. Comment /review to retry on a fresh agent.

XHarness did not produce the expected fresh result 'testResults.xml' for requested class(es) 'Microsoft.Maui.DeviceTests.ScrollViewHandlerTests' (the target tests did not run).

⚠️ Gate coverage limitations

• The A/B gate did not verify 1 dropped DeviceTest group(s): ViewTests (CustomViewSafeAreaEdgesReachMauiView, ChangingParentSafeAreaEdgesInvalidatesDescendants, MeasureInvalidatedParentDoesNotBlockDescendantSafeAreaInvalidation, ParentSafeAreaSuppressionDoesNotDependOnLayoutOrder, ResolvedBottomEdgeSkipsFartherAncestorKeyboardGeometry, ResidualParentInsetDoesNotSuppressChildSafeArea, ParentHandledEdgeLookupStopsWhenAllEdgesAreResolved, EmptySafeAreaSkipsParentHandledEdgeLookup, EmptyManualScrollViewSafeAreaSkipsParentHandledEdgeLookup, KeyboardSafeAreaChangesInvalidateDescendants, ParentContainerSafeAreaDoesNotSuppressChildKeyboardSafeArea, ParentAndChildKeyboardSafeAreasDoNotDoublePadArrangedChild, ParentAndChildKeyboardSafeAreasProtectOverflowingChild, HiddenKeyboardSkipsDuplicateSoftInputStrategyResolution, UnchangedKeyboardGeometryKeepsAncestorSafeAreaCache, ChangedKeyboardOverlapInvalidatesNonSoftInputDescendants, SoftInputAncestorInsideScrollViewDoesNotSuppressKeyboardAutoScroll, KeyboardFrameConvertsFromScreenToWindowCoordinates, FloatingKeyboardUsesClampedViewIntersection, NestedKeyboardSafeAreasUseCrossPlatformArrange, ParentOnlySuppressesOverlappingChildSafeAreaEdges, ParentOnlySuppressesOverlappingScrollViewSafeAreaEdges, SystemAdjustedScrollViewInsetsAreNotSuppressedByParent, ChangingAncestorSafeAreaEdgesInvalidatesEdgeDisjointGrandchild). Deep UI Tests runs HostApp UI categories only and does not execute DeviceTests; separate device-test validation is required.

/Users/cloudtest/vss/_work/1/s/src/Controls/tests/Core.UnitTests/SafeAreaTests.cs(577,35): error CS0539: 'SafeAreaTests.DerivedSafeAreaContentPage.GetDefaultSafeAreaEdges()' in explicit interface declaration is not found among members of the interface that can be implemented [/Users/cloudtest/vss/_work/1/s/src/Controls/tests/Core.UnitTests/Controls.Core.UnitTests.csproj]
/Users/cloudtest/vss/_work/1/s/src/Controls/tests/Core.UnitTests/SafeAreaTests.cs(583,26): error CS0539: 'SafeAreaTests.DerivedDefaultSafeAreaContentPage.HasExplicitSafeAreaEdges' in explicit interface declaration is not found among members of the interface that can be implemented [/Users/cloudtest/vss/_work/1/s/src/Controls/tests/Core.UnitTests/Controls.Core.UnitTests.csproj]
/Users/cloudtest/vss/_work/1/s/src/Controls/tests/Core.UnitTests/SafeAreaTests.cs(584,35): error CS0539: 'SafeAreaTests.DerivedDefaultSafeAreaContentPage.GetDefaultSafeAreaEdges()' in explicit interface declaration is not found among members of the interface that can be implemented [/Users/cloudtest/vss/_work/1/s/src/Controls/tests/Core.UnitTests/Controls.Core.UnitTests.csproj]
/Users/cloudtest/vss/_work/1/s/src/Controls/tests/Core.UnitTests/SafeAreaTests.cs(597,26): error CS0539: 'SafeAreaTests.CustomNoneSafeAreaView.HasExplicitSafeAreaEdges' in explicit interface declaration is not found among members of the interface that can be implemented [/Users/cloudtest/vss/_work/1/s/src/Controls/tests/Core.UnitTests/Controls.Core.UnitTests.csproj]
/Users/cloudtest/vss/_work/1/s/src/Controls/tests/Core.UnitTests/SafeAreaTests.cs(599,35): error CS0539: 'SafeAreaTests.CustomNoneSafeAreaView.GetDefaultSafeAreaEdges()' in explicit interface declaration is not found among members of the interface that can be implemented [/Users/cloudtest/vss/_work/1/s/src/Controls/tests/Core.UnitTests/Controls.Core.UnitTests.csproj]
/Users/cloudtest/vss/_work/1/s/src/Controls/tests/Core.UnitTests/SafeAreaTests.cs(612,26): error CS0539: 'SafeAreaTests.CustomMixedSafeAreaView.HasExplicitSafeAreaEdges' in explicit interface declaration is not found among members of the interface that can be implemented [/Users/cloudtest/vss/_work/1/s/src/Controls/tests/Core.UnitTests/Controls.Core.UnitTests.csproj]
/Users/cloudtest/vss/_work/1/s/src/Controls/tests/Core.UnitTests/SafeAreaTests.cs(614,35): error CS0539: 'SafeAreaTests.CustomMixedSafeAreaView.GetDefaultSafeAreaEdges()' in explicit interface declaration is not found among members of the interface that can be implemented [/Users/cloudtest/vss/_work/1/s/src/Controls/tests/Core.UnitTests/Controls.Core.UnitTests.csproj]
/Users/cloudtest/vss/_work/1/s/src/Controls/tests/Core.UnitTests/SafeAreaTests.cs(497,43): error CS0535: 'SafeAreaTests.CustomSafeAreaView' does not implement interface member 'ISafeAreaElement.SafeAreaEdgesDefaultValueCreator()' [/Users/cloudtest/vss/_work/1/s/src/Controls/tests/Core.UnitTests/Controls.Core.UnitTests.csproj]
/Users/cloudtest/vss/_work/1/s/src/Controls/tests/Core.UnitTests/SafeAreaTests.cs(524,43): error CS0535: 'SafeAreaTests.CustomSafeAreaPage' does not implement interface member 'ISafeAreaElement.SafeAreaEdgesDefaultValueCreator()' [/Users/cloudtest/vss/_work/1/s/src/Controls/tests/Core.UnitTests/Controls.Core.UnitTests.csproj]
/Users/cloudtest/vss/_work/1/s/src/Controls/tests/Core.UnitTests/SafeAreaTests.cs(587,47): error CS0535: 'SafeAreaTests.CustomNoneSafeAreaView' does not implement interface member 'ISafeAreaElement.SafeAreaEdgesDefaultValueCreator()' [/Users/cloudtest/vss/_work/1/s/src/Controls/tests/Core.UnitTests/Controls.Core.UnitTests.csproj]
/Users/cloudtest/vss/_work/1/s/src/Controls/tests/Core.UnitTests/SafeAreaTests.cs(602,48): error CS0535: 'SafeAreaTests.CustomMixedSafeAreaView' does not implement interface member 'ISafeAreaElement.SafeAreaEdgesDefaultValueCreator()' [/Users/cloudtest/vss/_work/1/s/src/Controls/tests/Core.UnitTests/Controls.Core.UnitTests.csproj]

Default [< 1 ms]
  Passed SafeAreaEdgesTypeConverter_ConvertFromFourValues [< 1 ms]
  Passed IsSafeAreaEdgesSet_NullBindableThrows [< 1 ms]
  Passed SafeAreaEdgesTypeConverter_ConvertFromInvalidValue_ThrowsException [< 1 ms]
  Passed SafeAreaEdges_UniformConstructor_AppliesAllEdges [< 1 ms]
  Passed StackLayouts_RespectUserSettings [< 1 ms]
  Passed GetEdgeValue_TwoValues_AppliesCorrectly [< 1 ms]
  Passed CustomView_DefaultRegionsUseDeclaredEdges [< 1 ms]
  Passed GetEdgeValue_FourValues_AppliesCorrectly [< 1 ms]
  Passed SafeAreaEdgesTypeConverter_ConvertFromInvalidLength_ThrowsException [< 1 ms]
  Passed Layout_ImplementsISafeAreaView [< 1 ms]
  Passed SafeAreaEdges_AllEnumValues_WorkCorrectly [< 1 ms]
[xUnit.net 00:00:00.67]   Finished:    Microsoft.Maui.Controls.Core.UnitTests
  Passed CustomPage_CanOverrideInheritedSafeAreaStrategy [< 1 ms]
  Passed CustomView_CanReuseSafeAreaEdgesContract [< 1 ms]
  Passed StackLayout_HorizontalOrientation_RespectsDirectProperty_RTL [< 1 ms]
  Passed GetEdges_DefaultValue_ReturnsDefault [< 1 ms]
  Passed HasExplicitSafeAreaEdges_StyleValueCountsAsExplicit [1 ms]
Test Run Successful.
Total tests: 77
     Passed: 77
 Total time: 0.8697 Seconds

/Users/cloudtest/vss/_work/1/s/src/Controls/tests/Xaml.UnitTests/SafeAreaEdgesTests.xaml.cs(91,25): error CS0539: 'CustomSafeAreaElement.HasExplicitSafeAreaEdges' in explicit interface declaration is not found among members of the interface that can be implemented [/Users/cloudtest/vss/_work/1/s/src/Controls/tests/Xaml.UnitTests/Controls.Xaml.UnitTests.csproj]
/Users/cloudtest/vss/_work/1/s/src/Controls/tests/Xaml.UnitTests/SafeAreaEdgesTests.xaml.cs(93,34): error CS0539: 'CustomSafeAreaElement.GetDefaultSafeAreaEdges()' in explicit interface declaration is not found among members of the interface that can be implemented [/Users/cloudtest/vss/_work/1/s/src/Controls/tests/Xaml.UnitTests/Controls.Xaml.UnitTests.csproj]
/Users/cloudtest/vss/_work/1/s/src/Controls/tests/Xaml.UnitTests/SafeAreaEdgesTests.xaml.cs(81,52): error CS0535: 'CustomSafeAreaElement' does not implement interface member 'ISafeAreaElement.SafeAreaEdgesDefaultValueCreator()' [/Users/cloudtest/vss/_work/1/s/src/Controls/tests/Xaml.UnitTests/Controls.Xaml.UnitTests.csproj]

aui.Controls.Xaml.UnitTests
[xUnit.net 00:00:02.95]   Starting:    Microsoft.Maui.Controls.Xaml.UnitTests
  Passed FourValueConversions(inflator: SourceGen) [26 ms]
  Passed FourValueConversions(inflator: XamlC) [< 1 ms]
  Passed FourValueConversions(inflator: Runtime) [24 ms]
  Passed SingleValueConversions(inflator: XamlC) [< 1 ms]
  Passed SingleValueConversions(inflator: SourceGen) [< 1 ms]
  Passed SingleValueConversions(inflator: Runtime) [1 ms]
  Passed TwoValueConversions(inflator: XamlC) [< 1 ms]
  Passed TwoValueConversions(inflator: Runtime) [1 ms]
  Passed TwoValueConversions(inflator: SourceGen) [< 1 ms]
[xUnit.net 00:00:03.05]   Finished:    Microsoft.Maui.Controls.Xaml.UnitTests
  Passed PropertyInflation_WorksWithAllEnumValues(inflator: XamlC) [1 ms]
  Passed PropertyInflation_WorksWithAllEnumValues(inflator: Runtime) [1 ms]
  Passed PropertyInflation_WorksWithAllEnumValues(inflator: SourceGen) [< 1 ms]
  Passed ControlSpecificProperties(inflator: Runtime) [4 ms]
  Passed ControlSpecificProperties(inflator: XamlC) [< 1 ms]
  Passed ControlSpecificProperties(inflator: SourceGen) [< 1 ms]
Test Run Successful.
Total tests: 15
     Passed: 15
 Total time: 3.2648 Seconds

/Users/cloudtest/vss/_work/1/s/src/Controls/tests/Xaml.UnitTests/SafeAreaEdgesTests.xaml.cs(91,25): error CS0539: 'CustomSafeAreaElement.HasExplicitSafeAreaEdges' in explicit interface declaration is not found among members of the interface that can be implemented [/Users/cloudtest/vss/_work/1/s/src/Controls/tests/Xaml.UnitTests/Controls.Xaml.UnitTests.csproj]
/Users/cloudtest/vss/_work/1/s/src/Controls/tests/Xaml.UnitTests/SafeAreaEdgesTests.xaml.cs(93,34): error CS0539: 'CustomSafeAreaElement.GetDefaultSafeAreaEdges()' in explicit interface declaration is not found among members of the interface that can be implemented [/Users/cloudtest/vss/_work/1/s/src/Controls/tests/Xaml.UnitTests/Controls.Xaml.UnitTests.csproj]
/Users/cloudtest/vss/_work/1/s/src/Controls/tests/Xaml.UnitTests/SafeAreaEdgesTests.xaml.cs(81,52): error CS0535: 'CustomSafeAreaElement' does not implement interface member 'ISafeAreaElement.SafeAreaEdgesDefaultValueCreator()' [/Users/cloudtest/vss/_work/1/s/src/Controls/tests/Xaml.UnitTests/Controls.Xaml.UnitTests.csproj]

or(targetPlatformIdentifier: "") [1 s]
  Passed SingleProject_NonPlatformBuildExcludesPlatformSpecificFoldersButKeepsSharedFolder [1 s]
  Passed RandomEmbeddedResource [1 s]
  Passed SingleProject_RecognizedTfmIgnoresNeutralBackendSelector [1 s]
  Passed TargetsShouldSkip [2 s]
[xUnit.net 00:01:53.69]     TouchXamlFile [SKIP]
[xUnit.net 00:01:53.69]       source gen changes
  Skipped TouchXamlFile [1 ms]
  Passed ItemDisplayBindingWithoutDataTypeFails(inflator: XamlC) [87 ms]
  Passed ItemDisplayBindingWithoutDataTypeFails(inflator: SourceGen) [4 ms]
  Passed ItemDisplayBindingWithoutDataTypeFails(inflator: Runtime) [3 ms]
  Passed RequiredFieldsAndPropertiesAreSet(inflator: XamlC) [< 1 ms]
  Passed RequiredFieldsAndPropertiesAreSet(inflator: SourceGen) [17 ms]
  Passed RequiredFieldsAndPropertiesAreSet(inflator: Runtime) [< 1 ms]
  Passed ThrowsOnMismatchingType(inflator: SourceGen) [6 ms]
  Passed ThrowsOnMismatchingType(inflator: XamlC) [39 ms]
[xUnit.net 00:01:53.85]   Finished:    Microsoft.Maui.Controls.Xaml.UnitTests
  Passed ThrowsOnMismatchingType(inflator: Runtime) [< 1 ms]
Test Run Successful.
Total tests: 2123
     Passed: 2115
    Skipped: 8
 Total time: 1.9021 Minutes

/Users/cloudtest/vss/_work/1/s/src/Controls/tests/DeviceTests/Elements/View/ViewTests.cs(93,26): error CS0539: 'ViewTests.CustomSafeAreaView.HasExplicitSafeAreaEdges' in explicit interface declaration is not found among members of the interface that can be implemented [/Users/cloudtest/vss/_work/1/s/src/Controls/tests/DeviceTests/Controls.DeviceTests.csproj::TargetFramework=net11.0-ios]
/Users/cloudtest/vss/_work/1/s/src/Controls/tests/DeviceTests/Elements/View/ViewTests.cs(95,35): error CS0539: 'ViewTests.CustomSafeAreaView.GetDefaultSafeAreaEdges()' in explicit interface declaration is not found among members of the interface that can be implemented [/Users/cloudtest/vss/_work/1/s/src/Controls/tests/DeviceTests/Controls.DeviceTests.csproj::TargetFramework=net11.0-ios]
/Users/cloudtest/vss/_work/1/s/src/Controls/tests/DeviceTests/Elements/View/ViewTests.cs(73,43): error CS0535: 'ViewTests.CustomSafeAreaView' does not implement interface member 'ISafeAreaElement.SafeAreaEdgesDefaultValueCreator()' [/Users/cloudtest/vss/_work/1/s/src/Controls/tests/DeviceTests/Controls.DeviceTests.csproj::TargetFramework=net11.0-ios]
Build FAILED.

PR #37750 Pre-Flight

Context

• Title: [net11.0] Expose safe area contract for custom views
• Base: net11.0
• Materialized review commit: d7905a8af8829a1a8da9fb8992aa9175551724ac
• Related issue: #37384, which reports that custom views cannot participate in the .NET 10 per-edge SafeAreaEdges model or expose an effective strategy to native hosts.
• Gate: Inconclusive because the existing test could not be built or run. This is not evidence that the PR fix fails, and gate verification must not be rerun in STEP 5a.

Current PR Approach

The PR replaces the internal numbered ISafeAreaView2 contract with a public ISafeAreaElement contract, adds explicit/default-value metadata and a public effective-strategy resolver, exposes reusable Controls bindable-property plumbing, and routes Apple/Android safe-area handling through a shared internal strategy resolver. It retains the shipped ISafeAreaView fallback and adds substantial unit, XAML, device, HostApp, AOT-profile, and platform behavior coverage.

The materialized diff changes 56 files (3020 insertions, 530 deletions), including:

• public API and Controls property plumbing (ISafeAreaElement, SafeAreaElement, API baselines);
• an internal compatibility resolver (ISafeAreaViewStrategy / SafeAreaViewStrategy);
• iOS MauiView, MauiScrollView, keyboard, inset, and handler paths;
• Android listener and inset paths;
• built-in control defaults and bindable-property specificity behavior;
• safe-area unit, XAML, Controls device, Core device, and AOT-profile coverage.

The diff adds ISafeAreaInsets.cs and ISafeAreaViewStrategy.cs and deletes ISafeAreaView2.cs; candidate attempts must obey the try-fix baseline allow-list and report Blocked if the baseline state contains any NewFiles.

Alternative-Fix Requirement

Each candidate must use a distinct root-cause hypothesis and must not reproduce the PR's shared public-contract-plus-central-resolver design. Candidate 2 must also avoid candidate 1's recorded mechanism.

Test Contract

Primary test:

pwsh .github/scripts/BuildAndRunHostApp.ps1 -Platform ios -TestFilter "SafeAreaEdges"

Only after the primary test passes, run every regression command supplied by the STEP 5a request, including repeated entries. Any regression failure makes the candidate Fail. A missing simulator/device is Blocked; build, compile, or script errors are Fail.

Each attempt allows one implementation/test pass and at most one focused correction/retest. The gate test must not be rerun, no full suite may be run, and the exact restore command is:

pwsh .github/scripts/EstablishBrokenBaseline.ps1 -Restore

Workspace Constraints

The checkout already contains numerous unrelated modified/untracked CI-script files. They predate STEP 5a and must not be edited, removed, restored, stashed, or included in candidate diffs. gate/content.md is owned by the prior gate phase and must not be created or overwritten.

Expert PR Evaluation — dotnet/maui #37750

Scope reviewed: local raw submitted commit d7905a8af8829a1a8da9fb8992aa9175551724ac against base ec79089f65, in read-only worktree /Users/cloudtest/vss/_work/1/s. Authoritative diff = git diff ec79089f65..d7905a8af8. The public PR head may have advanced remotely; that newer head was not reviewed or fetched. Unrelated dirty .github/eng files in the worktree were ignored.

Method: independence-first. The full diff and the relevant full files at d7905a8af8 (plus callers/consumers and prior behaviour at ec79089f65) were read before any PR narrative was consulted.

1. What the PR actually does (independent reading)

This is a safe-area contract refactor that converts an internal, page-centric interface into a public, per-edge extensibility contract, plus several behavioural changes to iOS safe-area/keyboard geometry.

Structural changes:

Behavioural changes (not merely mechanical):

1. ViewHandler.cs:81 — the SafeAreaEdges mapper registration moved from #if ANDROID || IOS to #if ANDROID || IOS || MACCATALYST. MACCATALYST is a distinct symbol from IOS in this repo (confirmed by the pervasive #if IOS || MACCATALYST idiom, e.g. ContentPage.cs), so the mapper was previously never registered on Mac Catalyst — runtime SafeAreaEdges changes did not propagate there at all. This is a genuine, previously-unfixed bug.
2. Specificity-aware handler updates — BindableProperty.UpdateHandlerOnSpecificityChange (new internal flag, set only for SafeAreaEdgesProperty), plumbed through BindableObject.OnBindablePropertySet (new specificityChanged parameter) into Element.OnBindablePropertySet. Assigning the same value at a different specificity now updates the handler, because explicitness itself changes resolution.
3. Ancestor suppression became per-edge and value-based — bool IsParentHandlingSafeArea() → SafeAreaEdges GetParentHandledSafeAreaEdges(), which recomputes each ancestor's adjusted insets rather than reading a cached bool, and ExcludeParentHandledSafeAreaEdges zeroes only overlapping edges.
4. Keyboard geometry rewritten — TryGetSoftInputBottomOverlap now converts the keyboard frame into window coordinates via window.ConvertRectFromCoordinateSpace(..., window.Screen.CoordinateSpace) and intersects against the view's own window-space frame (the old code compared _keyboardFrame against window.Frame and used Superview.ConvertRectToView(Frame, Window)). The !IsSoftInputHandledByParent(this) gate was removed and replaced by per-view frame-relative overlap plus bottomIncludesKeyboardOverlap.
5. New subtree invalidation — MauiView.InvalidateSafeArea(UIView) (static, recursive over all subviews) and InvalidateDescendantSafeAreas(), fired from keyboard callbacks and from MapSafeAreaEdges.

2. Independent assessment

The contract split is right. The old ISafeAreaView2 conflated three unrelated concerns — a per-edge resolution strategy, an inset write-back sink, and a public configuration surface — and forced every implementer (Border, ContentView, Layout, ScrollView, Page) to stub out the parts it did not need (Thickness ISafeAreaView2.SafeAreaInsets { set { } } appears four times in the deleted code). Splitting into ISafeAreaElement (public config) / ISafeAreaViewStrategy (internal resolution) / ISafeAreaInsets (internal sink) is correct layer placement, and centralising resolution in SafeAreaViewStrategy removes five near-duplicate GetSafeAreaRegionsForEdge implementations. The new types correctly live in src/Core so ISafeAreaElement is referenceable without adding Core interface deps to Controls.csproj — this matches the guidance in safe-area-ios.instructions.md.

Ordering in SafeAreaViewStrategy.TryGetSafeAreaEdges is ISafeAreaViewStrategy → ISafeAreaElement → (optionally) legacy ISafeAreaView, which preserves built-in compatibility behaviour while letting custom views opt into the modern contract. That is consistent across all four call sites, and includeLegacy: false is passed everywhere a legacy fallback would have changed existing behaviour.

The mechanical parts I verified as behaviour-preserving:

• SafeAreaPadding is (Left, Right, Top, Bottom); every new construction site passes them in that order (ExcludeParentHandledSafeAreaEdges, GetAdjustedSafeAreaInsets). SafeAreaEdges is (Left, Top, Right, Bottom); every new construction site matches. No positional-argument transposition.
• SetterSpecificity defines operator != (SetterSpecificity.cs:248), and originalSpecificity is captured before context.Values.SetValue(...) in SetValueActual, so specificityChanged is computed correctly. SetterSpecificityList.GetSpecificity() is O(1) (_top.Specificity), so the new per-set computation is negligible.
• MauiWindowInsetListener.HasExplicitSafeAreaEdges and SafeAreaExtensions.ApplyAdjustedSafeAreaInsetsPx retain equivalent type coverage after the swap (Page implements ISafeAreaViewStrategy; ContentPage implements ISafeAreaElement; both resolve to the same values as before).
• MauiScrollView is a UIScrollView, not a MauiView, so the if (MauiView) … else if (MauiScrollView) dispatch in InvalidateSafeArea is correct, not an accidental exclusive branch.
• ViewHandler.iOS.MapSafeAreaEdges uses handler.PlatformView is PlatformView platformView, which null-guards via the pattern; no NRE risk there.

Where I disagree with the change as submitted is concentrated in the iOS runtime behaviour, not the contract. Three items are load-bearing and, in my reading, regressions or unproven assumptions; the rest are cost/documentation concerns. Details in §3.

3. Findings with evidence

3.1 [major] — MauiScrollView lost ancestor suppression on the SystemAdjustedContentInset branch

MauiScrollView.cs:389:

_appliesSafeAreaAdjustments = RespondsToSafeArea() && !_safeArea.IsEmpty;

The !IsParentHandlingSafeArea() term was removed. Its replacement, ExcludeParentHandledSafeAreaEdges(_safeArea, GetParentHandledSafeAreaEdges()), is applied only inside the first branch (SystemAdjustedContentInset == UIEdgeInsets.Zero || ContentInsetAdjustmentBehavior == Never). The else branch is:

else
{
    // UIKit's adjusted inset is authoritative once the scroll view is scrollable.
    // Filtering it through MAUI ancestor padding would discard native scroll insets.
    _safeArea = SystemAdjustedContentInset.ToSafeAreaInsets();
}

No ancestor filtering, and _appliesSafeAreaAdjustments no longer gates on ancestors either. So for a scrollable ScrollView under a safe-area-applying MauiView ancestor, both now inset the same edges. Prior to this commit IsParentHandlingSafeArea() forced _appliesSafeAreaAdjustments = false in exactly that configuration.

Repro shape: ContentPage SafeAreaEdges="All" → VerticalStackLayout → ScrollView with content taller than the viewport (behavior stays Automatic, SystemAdjustedContentInset != Zero). This is the double-apply/oscillation family tracked by #33595 and #32586, and the comment justifying the carve-out ("UIKit's adjusted inset is authoritative") explains why UIKit's value should not be filtered, but does not address why the scroll view should still apply it when an ancestor already did.

Coverage: ScrollViewHandlerTests.iOS.cs adds exactly one test, LegacySafeAreaViewWithoutModernContractRemainsEdgeToEdge, which asserts ContentInsetAdjustmentBehavior == Never — i.e. it exercises the other branch. The regressed path has no test.

3.2 [major] — bottomIncludesKeyboardOverlap can permanently double keyboard padding

MauiView.cs:592:

!bottomIncludesKeyboardOverlap && parentHandledEdges.Bottom != SafeAreaRegions.None ? 0 : safeArea.Bottom

with the comment "Keep a child's positive frame-relative keyboard overlap until its parent arranges that child above the keyboard; the overlap is then zero and normal suppression applies."

That convergence argument holds only when the parent's bottom inset actually moves the child. It does not for a child that is bottom-aligned in a fixed-height row, absolutely positioned, or otherwise not repositioned by the parent's content-rect shrink. In those cases TryGetSoftInputBottomOverlap keeps returning a positive overlap indefinitely and both ancestor and descendant pad for the keyboard — roughly 2× keyboard height. The removed !IsSoftInputHandledByParent(this) gate is precisely what previously prevented this.

IsSoftInputHandledByParent still exists but is now only consumed by KeyboardAutoManagerScroll.AdjustPositionDebounce (KeyboardAutoManagerScroll.cs:309) — it no longer participates in inset computation at all.

3.3 [major] — layout-pass amplification and non-convergence risk

MauiView.cs:863 calls InvalidateDescendantSafeAreas() from inside ValidateSafeArea(), which runs on the layout path. Each descendant gets SetNeedsLayout() during a layout pass, and each descendant that changes then invalidates its own descendants.

Combined with §3.2's deliberate two-phase convergence, a single keyboard show on nested SoftInput edges costs a minimum of three passes (parent pads → child overlap resolves to 0 → parent re-measures). The EqualsAtPixelLevel guard in the return value (MauiView.cs:~866) terminates the loop only when values converge; it does not prevent a feedback cycle where the child's applied inset feeds back into the parent's arrange.

Related cost, same mechanism:

• MauiView.cs:554 — GetParentHandledSafeAreaEdges now calls mauiView.GetAdjustedSafeAreaInsets(...) per ancestor (interface type tests + virtual GetDefaultSafeAreaEdges() + struct construction + a 4-edge scan, plus ConvertRectToView/ConvertRectFromCoordinateSpace for the nearest ancestor). Previously: read a cached bool field. O(views × depth), and the _parentHandledSafeAreaEdges cache is nulled for every descendant on each change.
• MauiView.cs:976 — InvalidateSafeArea(UIView) recurses the entire native subtree with no early exit; each node's Subviews access marshals a fresh managed array. Fires on every keyboard show/hide/frame-change and on every MapSafeAreaEdges.
• ViewHandler.iOS.cs:167 — that full-subtree walk is now also triggered by specificity-only changes (via UpdateHandlerOnSpecificityChange), e.g. a Style re-applying the same SafeAreaEdges value or a VisualState re-entry.

Per repo convention, cache/hot-path changes of this shape need dotnet-trace/speedscope evidence; none is present in the diff.

3.4 [moderate] — ancestor region semantics are collapsed to a marker

MauiView.cs:567 and neighbours set left/top/right/bottom = SafeAreaRegions.Container purely as a "handled" marker, discarding the ancestor's actual region. A SoftInput-bottom ancestor (transient, keyboard-driven) therefore suppresses a Container-bottom child (persistent, home-indicator) for the duration of the keyboard session. Recording the ancestor's resolved region via SafeAreaViewStrategy.GetSafeAreaRegionsForEdge would let suppression apply only to genuinely overlapping semantics.

3.5 [moderate] — HasSoftInputBottomOverlapChanged() is a mutating predicate on the fast path

MauiView.cs:407. It mutates _lastSoftInputBottomOverlap, is non-idempotent within a pass, and runs before the !_safeAreaInvalidated early-return — so the steady-state "nothing changed" path now always pays a TryGetSafeAreaEdges call and, with the keyboard up, two coordinate conversions per layout.

3.6 [moderate] — bindable-property specificity coverage gap

Element.cs:711. The forward direction (setting a value at a new specificity) is covered. The reverse — ClearValue/style-unapply causing HasExplicitSafeAreaEdges to flip back to false — depends on the new original.Key != bpcontext.Values.GetSpecificity() check at BindableObject.cs:152, and SafeAreaTests.cs (+517 lines) contains no test exercising it. Note also that SetValueActual's if (specificity < originalSpecificity) branch returns without calling OnBindablePropertySet at all (pre-existing), so the specificity-change signal is deliberately partial.

3.7 [moderate] / [minor] — public-surface polish

• SafeAreaElementExtensions.GetEffectiveSafeAreaEdges (ISafeAreaElement.cs:61) is documented as returning "the per-edge safe area strategy consumed by MAUI platform handlers", but handlers layer keyboard state and ancestor suppression on top of that value, so it does not describe what is applied. It also has no in-repo consumer.
• SafeAreaElement.IsSafeAreaEdgesSet (SafeAreaElement.cs:57) silently returns false for a BindableObject that declares its own SafeAreaEdges property rather than reusing the shared instance — a silent degradation in a newly public extensibility contract.
• Page.cs:268–271's new this is ISafeAreaElement branch is unreachable for every built-in Page subclass (ContentPage re-implements the interface explicitly; all others never implement ISafeAreaElement). It exists only for user subclasses and has no test.

4. Public API and compatibility assessment

Additions are correctly declared. PublicAPI.Unshipped.txt was updated for all 7 Controls RIDs and all 8 Core RIDs. Core entries:

Microsoft.Maui.ISafeAreaElement
Microsoft.Maui.ISafeAreaElement.SafeAreaEdges.get -> Microsoft.Maui.SafeAreaEdges
Microsoft.Maui.ISafeAreaElement.HasExplicitSafeAreaEdges.get -> bool
Microsoft.Maui.ISafeAreaElement.GetDefaultSafeAreaEdges() -> Microsoft.Maui.SafeAreaEdges
Microsoft.Maui.SafeAreaElementExtensions
static Microsoft.Maui.SafeAreaElementExtensions.GetEffectiveSafeAreaEdges(...) -> Microsoft.Maui.SafeAreaEdges

Controls entries add SafeAreaElement, SafeAreaElement.IsSafeAreaEdgesSet, SafeAreaElement.SafeAreaEdgesProperty. These match the actual shapes. PublicAPI.Shipped.txt was not touched — correct.

No breaking change to shipped API. ISafeAreaView2 and the old ISafeAreaElement were both internal, so their deletion/reshaping is invisible to consumers. SafeAreaEdgesDefaultValueCreator() → GetDefaultSafeAreaEdges() is an internal-to-public rename with no shipped predecessor. The public instance SafeAreaEdges properties on Border/ContentView/Layout/ScrollView/ContentPage already existed at the base commit and are unchanged.

Forward-compatibility risk to flag for the API council, not a blocker: ISafeAreaElement is now a public interface with three members. Adding a member to it later is a breaking change (default interface method / IFoo2 / extension method would be required). Given that the design explicitly justifies why all three members are needed, this is defensible — but SafeAreaElementExtensions.GetEffectiveSafeAreaEdges (§3.7) is the piece I would not ship without a demonstrated consumer, since public static extensions on a public contract cannot be withdrawn.

Behavioural compatibility: the Mac Catalyst mapper registration change (#if ANDROID || IOS → + || MACCATALYST) is a behaviour change on Mac Catalyst — runtime SafeAreaEdges mutations now take effect where they previously silently did nothing. That is the intended fix, but Mac Catalyst apps that inadvertently depended on the property being inert will see layout shifts. Worth a release note. Mac Catalyst also defaults UseSafeArea to true (unlike iOS), and ContentPage's new explicit ISafeAreaElement.SafeAreaEdges getter routes the unset case through ((ISafeAreaView)this).IgnoreSafeArea under #if IOS || MACCATALYST, which preserves that asymmetry correctly.

Default-value semantics for third parties: a custom view implementing only ISafeAreaElement and returning SafeAreaEdges.Default from GetDefaultSafeAreaEdges() resolves to Container (SafeAreaViewStrategy.ResolveDefaultRegion), which differs from every built-in control's default (Border/ContentView/ContentPage = None, Layout = Container, ScrollView = unresolved Default). This is documented in the interface remarks and appears deliberate, but it is a divergence third-party authors will hit.

5. Blast radius

High. This is not a localised fix.

• Types whose interface list changed: Border, ContentPage, ContentView, Layout (base of every layout panel), Page (base of every page), ScrollView. Layout and Page sit under essentially all MAUI content.
• Framework-wide plumbing: BindableObject.OnBindablePropertySet gained a parameter, overridden in Element and InputView. Element.OnBindablePropertySet runs for every bindable property set on every element — the specificityChanged computation is now unconditional there. It is O(1), but the code path is the single hottest one in Controls.
• iOS/Mac Catalyst layout core: MauiView (+354/-… lines) and MauiScrollView are the base platform views for nearly all MAUI content on Apple platforms. The safe-area/keyboard changes affect every page, every scroll view, and every CollectionView cell backed by a MauiView.
• Android: ViewHandler.Android.cs gained an IsModernSafeAreaView early-return in MapSafeAreaEdges, and SafeAreaExtensions/MauiWindowInsetListener were re-pointed at the new resolver. Coverage looks equivalent, but the inset pipeline is shared by all Android views.
• Platforms not exercised by the new tests: Windows and Tizen get new PublicAPI.Unshipped.txt entries (the interfaces are in the shared netstandard/net surface) but no behavioural coverage — acceptable, since the mapper is #if ANDROID || IOS || MACCATALYST.
• AOT/trimming: no reflection, no Type.GetType/Activator.CreateInstance, no new suppressions or DynamicallyAccessedMembers. SafeAreaViewStrategy resolves via plain is-pattern type tests, which are trimmer- and AOT-safe. The .aotprofile binaries were regenerated (small deltas, consistent with the removed ISafeAreaView2 dispatch). No AOT/trimming concerns.
• XAML: SafeAreaEdgesTests.xaml/.xaml.cs gained coverage; the shared SafeAreaEdgesProperty is still surfaced per-type through each control's own public static field, so XAML addressability is preserved (the interface remarks explicitly call this out).

6. Hard failure-mode probes

7. Test and gate evidence status

Tests added (substantial, and largely well-targeted):

Test types are placed in the right projects (XAML tests in Xaml.UnitTests, handler tests in Core/tests/DeviceTests, control tests in Controls/tests/DeviceTests), and iOS device tests compile for Mac Catalyst, which gives incidental coverage of the P2 fix.

Identified coverage gaps (each maps to a finding):

1. Scrollable ScrollView nested under a safe-area-applying ancestor — the branch regressed in §3.1. The one new ScrollViewHandlerTests.iOS.cs test covers the opposite branch.
2. Nested SoftInput bottom where the parent's inset does not reposition the child (§3.2).
3. Layout-pass count / non-oscillation assertion for a keyboard show over nested SoftInput edges (§3.3).
4. ClearValue/style-unapply on SafeAreaEdgesProperty flipping HasExplicitSafeAreaEdges back to false (§3.6).
5. A custom Page subclass implementing ISafeAreaElement, exercising the new Page.cs:268 branch (§3.7).
6. No dotnet-trace/speedscope evidence for the hot-path changes in §3.3, which repo convention requires for cache replacement.

Gate: the supplied gate is INCONCLUSIVE due to a build/environment error. Per the review instruction, this is explicitly not treated as a failing verification and does not by itself drive the verdict. Consequently I have no compile or test-execution evidence for this commit and this review is static-analysis-only; every finding above is derived from reading the diff, the full files at d7905a8af8, and the prior behaviour at ec79089f65. The claims most sensitive to that limitation are §3.2 and §3.3, whose failure modes are geometric and would be confirmed or refuted quickly on a device.

8. Verdict

NEEDS_CHANGES

Rationale. The architectural core of this PR — splitting ISafeAreaView2 into ISafeAreaElement / ISafeAreaViewStrategy / ISafeAreaInsets, centralising resolution in SafeAreaViewStrategy, and making the configuration contract public — is well-designed, correctly layered, properly declared in PublicAPI.Unshipped.txt, AOT/trim-clean, and backed by a genuinely large test addition. The Mac Catalyst mapper registration is a real bug fix. I would be comfortable with all of that.

The verdict is driven by one concrete regression and one unproven convergence assumption, both in iOS runtime geometry, both in code paths that sit under essentially every MAUI page:

1. §3.1 (blocking) — MauiScrollView.cs:389 drops ancestor suppression on the SystemAdjustedContentInset branch, where the replacement ExcludeParentHandledSafeAreaEdges call is unreachable. This re-opens the double-apply configuration behind #33595/#32586 for the most common scroll case (content taller than viewport), and the single new scroll-view test covers the other branch. This needs either the exclusion applied to that branch or the gate restored, plus a regression test named against the issue.
2. §3.2 (blocking) — removing !IsSoftInputHandledByParent(this) from inset computation in favour of bottomIncludesKeyboardOverlap is only self-correcting when the parent's inset repositions the child. A bottom-aligned or absolutely-positioned SoftInput child yields permanent double keyboard padding. This needs either a bound on the fallback or a device test proving convergence for a child the parent does not move.
3. §3.3 (needs evidence, not necessarily a code change) — the ancestor walk changed from reading a cached bool to recomputing each ancestor's full adjusted insets, and safe-area invalidation now recurses whole native subtrees on every keyboard event and every MapSafeAreaEdges (including specificity-only no-op updates). Per repo convention for cache replacement on a hot path, this needs dotnet-trace numbers before merge.

§3.4–§3.7 are non-blocking and can be addressed in follow-up, with one exception I would like resolved before merge because it cannot be withdrawn later: SafeAreaElementExtensions.GetEffectiveSafeAreaEdges should either have its documentation corrected or be dropped, since it is a new public static on a new public interface with no in-repo consumer and a doc comment that overstates what it returns.

Because the gate is inconclusive rather than red, none of the above rests on a failed build; all of it rests on the diff itself. If §3.1 and §3.2 are shown by device testing to be non-issues (i.e. the else branch is genuinely unreachable in practice for nested scroll views, and the overlap always converges), this moves to LGTM pending only the §3.3 trace and the §3.7 API note.

Confidence: high on §3.1 (the unreachable-guard argument is purely structural and does not depend on runtime behaviour); medium-high on §3.2 and §3.3 (the failure geometry is clear but unverified on device, as the gate could not run).

PR #37750 — STEP 5a Try-Fix Aggregate

Candidate 1 — Handler-Mapped Attached Safe-Area State

Model: claude-opus-5
Result: Blocked
Files changed: None
Self-review: 0 findings
Candidate narrative: ../try-fix-1/content.md
Attempt artifacts: attempt-1/

Approach

Expose safe-area configuration as an attached Controls property on any VisualElement, carry it through the existing ViewHandler property mapper, and push the resolved four-edge value onto MauiView/MauiScrollView as host-owned state. Keep the shipped ISafeAreaView fallback unchanged.

This avoids PR #37750's public ISafeAreaElement plus centralized strategy-resolver design. The PR fixes an unrecognized custom view by broadening a host-side type-identity pull; candidate 1 instead removes the recognition step. A handler mapper pushes data to the native host, so participation depends on the existing handler pipeline rather than implementation of a new MAUI interface.

Result and Failure Analysis

The approach was designed but not implemented. EstablishBrokenBaseline.ps1 rejected the pre-existing dirty worktree before creating .github/.baseline-state.json, so no RevertedFiles edit allow-list existed. The unrelated .github/scripts, .github/skills, and eng/scripts changes are off-limits and cannot be cleaned by an attempt. Independently, the PR adds ISafeAreaInsets.cs and ISafeAreaViewStrategy.cs; a successfully generated baseline would therefore contain NewFiles, which also requires Blocked.

The candidate diff is empty. The primary SafeAreaEdges HostApp command was skipped because no fix could be applied. All 13 supplied regression commands were consequently skipped because they are gated on primary-test success. The required restore command ran and reported the expected no-state result: No baseline state found / Restored False; no attempt-created changes existed.

Candidate 2 must avoid the attached-property, handler-mapper push, and native-host-owned strategy mechanism.

Candidate 2 — Version Existing ISafeAreaView

Model: gpt-5.6-sol
Result: Blocked
Files changed: None
Self-review: 0 findings
Candidate narrative: ../try-fix-2/content.md
Attempt artifacts: attempt-2/

Approach

Extend the already-public, already-recognized ISafeAreaView with a getter-only per-edge strategy and default interface behavior. Existing implementations would map IgnoreSafeArea to all-None or all-Container; custom views could override the per-edge member through a concrete bindable/XAML property. Apple hosts would continue pulling through the existing contract identity.

This differs from both earlier mechanisms. It neither introduces PR #37750's second public contract and centralized compatibility resolver nor uses candidate 1's attached property and handler-mapper push. It addresses missing expressiveness by versioning the public contract native hosts already recognize, with default interface members providing legacy compatibility.

Result and Failure Analysis

The approach was designed but not implemented. Baseline setup again rejected the pre-existing dirty tracked CI/script files and left .github/.baseline-state.json absent, so there was no RevertedFiles edit allow-list. The PR's added production files would independently force Blocked through the NewFiles rule.

The candidate diff is empty. The primary SafeAreaEdges HostApp command was skipped because no implementation could legally be applied. All 13 supplied regression commands were skipped because the primary did not pass. The required restore command ran and reported the expected no-state result: No baseline state found / Restored False; no attempt-created changes existed.

Aggregate Outcome

Two distinct alternative mechanisms were produced, satisfying the two-candidate cap, but neither could be implemented or empirically evaluated under the enforced baseline boundary. Both results are Blocked, not Fail: no compile, runtime, simulator, primary-test, or regression-test evidence was obtained. STEP 5b should assess the current PR code on its merits without treating either blocked candidate or the inconclusive gate as evidence against it.

⚠️ Final Recommendation: REQUEST CHANGES

Winner: pr

The raw submitted PR is the comparative winner because it is the only implemented candidate with a passing required regression record: all 13 issue-specific iOS regressions passed. This is not an approval. The trusted Gate remains inconclusive, the expert evaluation identified unresolved Apple-platform correctness/performance concerns, and the functionally equivalent pr-plus-reviewer runtime path failed one focused SafeAreaEdges test.

Comparative ranking

Expert review reconciliation

The expert pass correctly identified three low-risk improvements: the public GetEffectiveSafeAreaEdges() documentation described final handler behavior too strongly, the keyboard-overlap helper name hid mutation, and the reverse ClearValue specificity transition lacked a focused test. These are captured in pr-plus-reviewer/reviewer.patch.

Two proposed runtime reversions were not safe to apply in the single refinement:

• SystemAdjustedScrollViewInsetsAreNotSuppressedByParent explicitly establishes that UIKit-adjusted scroll insets remain authoritative when an ancestor has a safe area. Applying ancestor filtering to that branch would reverse submitted behavior without a reproducer.
• ParentAndChildKeyboardSafeAreasProtectOverflowingChild explicitly requires a non-repositioned child to retain its frame-relative keyboard overlap, while ParentAndChildKeyboardSafeAreasDoNotDoublePadArrangedChild verifies suppression after the child is repositioned. Restoring an all-or-nothing parent gate would regress the overflowing-child case.

The expert's hot-path concern remains unresolved: recursive descendant invalidation and per-ancestor adjusted-inset resolution have broad layout cost, and no trace comparison is available. More importantly, the one-shot candidate validation exposed a direct runtime failure in VerifyRuntimeSafeAreaEdgesChange; because the candidate's runtime code differs only by a private rename, that result creates uncertainty about the submitted behavior rather than demonstrating a reviewer-patch regression.

Required disposition

Request changes to resolve or explain the VerifyRuntimeSafeAreaEdgesChange failure and provide evidence for the unresolved Apple safe-area propagation/performance concerns. The inconclusive Gate is recorded as uncertainty and is not, by itself, the reason for this recommendation.

🔍 Regression Cross-Reference

✗ Revert risks detected — this PR removes 3 line(s) previously added by labeled bug-fix PRs.

Action required: Verify that issues #32586, #33595, #33934, #34042 do not re-regress before merging.

🧪 Regression Tests to Verify

These tests were added by the fix PRs being reverted. They must still pass:

🧪 Regression Test Results

✅ PASSED — 13 passed, 0 failed, 0 skipped

Detected UI test categories: Border,Layout,Page,SafeAreaEdges,ScrollView,ViewBaseTests

✅ Deep UI tests — 661 passed, 0 failed, 6 skipped across 6 categories on platform-pool agent (replaces in-process counts above).

🧪 UI Test Execution Results (deep, platform pool)